Skip to content

Conversation

@priyansh-narang2308
Copy link

Re-opening this as a new PR because the previous one (#15) was closed due to a repository deletion mishap. All changes are the same

@Devpool-soc
Copy link
Collaborator

Hey @priyansh-narang2308! Thank you for opening a pull request. Make sure to tag the maintainers and link the issue you are solving in your pull-request description if you have not already and they'll review as soon as possible.

@priyansh-narang2308
Copy link
Author

Hey @Ashrockzzz2003 Sorry for that , here is the new PR with the same changes

@Ashrockzzz2003
Copy link
Member

It'll help if you can update the README or add one for this

@Ashrockzzz2003
Copy link
Member

/bounty 500 @priyansh-narang2308

@Devpool-soc
Copy link
Collaborator

Another day, another coin. Way to get that bounty @priyansh-narang2308 you glorious keyboard-tapping, coffee-sipping, vibe-coding witcher!

@Ashrockzzz2003
Copy link
Member

/impact @priyansh-narang2308

@Devpool-soc
Copy link
Collaborator

What an IMPACT! Consider my tiny, shriveled heart officially impressed. Now, go and grab yourself a latte @priyansh-narang2308. You have earned it!

@priyansh-narang2308
Copy link
Author

sure will add the readme

minio-access-key: <BASE64_ENCODED_VALUE>
minio-secret-key: <BASE64_ENCODED_VALUE>
rabbitmq-url: <BASE64_ENCODED_VALUE>
rabbitmq-queue-name: <BASE64_ENCODED_VALUE>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its redis now as per the repo code...check out runner_controller, runner

secretKeyRef:
name: evolve-secrets
key: minio-secret-key
- name: RABBITMQ_URL
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its redis now, rabbitmq no longer there. check out repo

secretKeyRef:
name: evolve-secrets
key: minio-secret-key
- name: RABBITMQ_URL
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same goes here

@Ashrockzzz2003
Copy link
Member

Ashrockzzz2003 commented Jan 9, 2026

the deployment should've failed
how'd it succeed?

Check out docker/docker-compose.yml for the latest env vars and deps

@priyansh-narang2308
Copy link
Author

The deployment succeede in k8s coz the manifests were syntactically valid,but the pods wudhave failed at runtime. I've now updated to use Redis and synced the env with the docker-compose.yml

@Ashrockzzz2003
Copy link
Member

Can you also add a step where we got the test endpoint in each pod to determine if it's healthy

And then actually try the app that comes up after deployment to see if it works?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use kubernetes and add playbook tasks to deploy EvOC microservices in infra.

4 participants